What

• add embedded alice-workspace conversation ask and conversation read
• resume the exact originating runtime conversation by product resumeId
• fall back to a fresh headless worker in an owning Workspace when provenance is absent
• expose normalized assistant text, tool status, and errors without leaking native runtime session IDs
• centralize the configured/default Workspace runtime choice across interactive, Quick Chat, headless, and embedded CLI paths

Why

An internal Alice agent should be able to ask the agent that produced an Issue or Inbox entry why it made that call. This stays inside the Workspace service instead of looping through the public HTTP API.

Real workflow validation

• resumed the Pi conversation behind a real thesis Inbox entry; the reply recovered the original WIND-DOWN rationale, trigger, and falsifiers from its existing context
• started a fresh Pi worker in a different Workspace when no origin was available; it read the owning issue file and reconstructed the report rules
• observed normalized tool activity during polling (completed read tool) and a final assistant reply

Verification

• pnpm vitest run src/workspaces/conversation-control.spec.ts src/tool/conversation.spec.ts src/server/cli-commands.spec.ts src/server/cli.spec.ts src/workspaces/cli/shim.spec.ts src/webui/routes/workspaces.spec.ts src/webui/routes/workspaces-quickchat.spec.ts (87 passed)
• npx tsc --noEmit
• pnpm test (2537 passed, 6 skipped)
• git diff --check

Draft by design: parallel contribution mode, awaiting product review; do not merge automatically.